The dom0_ops implementation wasn't matching the interface definition,
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Wed, 4 Jan 2006 17:51:38 +0000 (18:51 +0100)
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Wed, 4 Jan 2006 17:51:38 +0000 (18:51 +0100)
commitdc88367fa15eb83d2372210b5fe1fb6c0c771946
treed86d1a931d35302fb900faadf4078bde58ed41ee
parentc546f7e7bbd31a38e7ba41095e01b9bcab197efe
The dom0_ops implementation wasn't matching the interface definition,
leading to ill messages when X starts up (and potentially to other
problems). The attached patch fixes that. However, it also points out
that there is a potential disagreement between the dom0_ops interface
and the internal MTRR interface - the former expects an unsigned
register number from the domain, the latter wants a signed one and does
a lookup when it's negative. I would think that the lookup code should
just be ripped out of xen/arch/x86/mtrr/main.c.

Signed-off-by: Jan Beulich <JBeulich@novell.com>
xen/arch/x86/dom0_ops.c